server: Cleanup dhcp and dns entries only on expunging VM#3608
server: Cleanup dhcp and dns entries only on expunging VM#3608yadvr merged 1 commit intoapache:4.13from
Conversation
This fixes a behaviour to not cleanup DHCP and DNS rules for NICs of a VM in the VR when it is stopped, but instead when VM is expunged because stopped VMs in CloudStack still retain the IPs and records. Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
|
@blueorangutan package |
|
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-290 |
|
@blueorangutan test |
|
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
shwstppr
left a comment
There was a problem hiding this comment.
LGTM on changes!
Although dhcp cleanup on VM stop seems more logical to me.
|
FYI - this partially reverts and refactors changes introduced in #3351 to cleanup VM dhcp/dns rules in the VR only when a VM is expunged. A VM hostname and IP address is used as constraint and checks even of a VM is stopped, i.e. you cannot deploy a VM with the same hostname and IP in a network with an existing VM with those attributes. This was tested against a local monkeybox KVM env and regression tested agains Trillian/kvm. |
According comment in PR apache#3608, dhcp and dns entries are cleaned up only when a VM is expunged. Revert part of commit 8fb388e.
This fixes a behaviour to not cleanup DHCP and DNS rules for NICs of a
VM in the VR when it is stopped, but instead when VM is expunged because
stopped VMs in CloudStack still retain the IPs and records.
Types of changes